Data description in this folder
===============================

Bat2 Connect demo data/                                    // This folder contains demo data in the same way as real BAT2 Connect scale store them in USB flash drive. It contains 3 export folders (name start with EXPORT) and 4 settings (files with suffix *.b2s). It means that 3 times were in scale called "Copy statistics". Each call "Copy statistics" save to USB drive export folder with samples and statistics and also it save actual configuration to *.b2s file. Last configuration file (4th) was created manually by user, see more details below in comment.
|- EXPORT-1708100696-XE4X9K862K9I6XQX88PX/                 // 1st export - BAT2 Connect scale has started weighing. It is 1st weighing for this scale ever. So statistics contains only 1 day (weighing day 18)
|  |- Events-2024_02_16__08_01_12.csv                      // Weight samples
|  |- Records-2024_02_16__08_01_12.csv                     // Statistics
|- EXPORT-1708252241-XE4X9K862K9I6XQX88PX/                 // 2nd export - contain another statistics and sample file, beacuse origin weighing was stopped and another one was started. But this new weighing started 2024/02/18 (reflected in file names) has no data.
|  |- Events-2024_02_16__08_01_12.csv                      //
|  |- Events-2024_02_18__10_23_51.csv                      //
|  |- Records-2024_02_16__08_01_12.csv                     //
|  |- Records-2024_02_18__10_23_51.csv                     //
|- EXPORT-1709122061-House-023/                            // 3rd export - different folder name. Previous exports contain scale serial number in name. Now we set in scale its name. If it setted, then it shows in export folder name. In this example scale has name "House-023". This export contains the same files as previous (2nd) plus another 2 new files (because we started new weighing - flock). This last weighing has no data for the first 10 days, only last day have 6 weighing samples. 
|  |- Events-2024_02_16__08_01_12.csv                      //
|  |- Events-2024_02_18__10_23_51.csv                      //
|  |- Events-2024_02_18__14_03_01.csv                      //
|  |- Records-2024_02_16__08_01_12.csv                     //
|  |- Records-2024_02_18__10_23_51.csv                     //
|  |- Records-2024_02_18__14_03_01.csv                     //
|- settings-2024_02_16__16_24_56-XE4X9K862K9I6XQX88PX.b2s  // 1st configuration - ethernet communication variant
|- settings-2024_02_18__10_30_41-XE4X9K862K9I6XQX88PX.b2s  // 2nd configuration - configuration was not modified
|- settings-2024_02_24__23_32_41-House-023.b2s             // 3rd configuration - scale has set it name to "House-023". It is inside scale part of configuration and also it is reflected in configuration file name.
|- settings-wifi.b2s                                       // 4rd configuration - this configuration was created by user manually. He copied 3rd configuration file and change communication from ethernet to wifi. See differences in files. Here is example how you can modify configuration for your another scale which has different communication channel (wifi). Other scale properties stayed unmodified. Another approach: When a user made a copy of configuration he he didn't even have to disable ethernet configuration. He could only add appropriate wifi settings and load it to him scale. The scale itself recognizes which communication settings it should use.
|- scale_data.json                                         // Example of JSON data that BAT2 Connect scale sends to API. This example is unminify - contains white spaces for better readability. Real data are sent in minify format. This file is only one that it not typically stored in USB drive. Here is only as example of data that scales send. Same data you will receive in your API server.
